Skip to content

Add GSSP fallback implementation #447

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
May 27, 2025

Conversation

pablothedude
Copy link
Contributor

@pablothedude pablothedude commented May 6, 2025

@pablothedude pablothedude marked this pull request as draft May 6, 2025 13:38
@pablothedude pablothedude force-pushed the feature/add-azure-mfa-registration-fallback branch 4 times, most recently from 4fd3cd8 to bd0cec2 Compare May 6, 2025 14:32
@pablothedude pablothedude force-pushed the feature/add-azure-mfa-registration-fallback branch 4 times, most recently from fd31d57 to feab5b3 Compare May 7, 2025 09:11
@pablothedude pablothedude force-pushed the feature/add-azure-mfa-registration-fallback branch from feab5b3 to 3767e04 Compare May 12, 2025 08:21
Copy link
Contributor

@parijke parijke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Paar kleine suggesties, verder ziet het er prima uit mijns inziens

This will allow the token fallback without the need of an entity.
@pablothedude pablothedude force-pushed the feature/add-azure-mfa-registration-fallback branch from d31ca41 to 39aafbe Compare May 19, 2025 09:10
@pablothedude pablothedude force-pushed the feature/add-azure-mfa-registration-fallback branch from 5b7d893 to e9464b4 Compare May 20, 2025 07:29
@pablothedude pablothedude force-pushed the feature/add-azure-mfa-registration-fallback branch 2 times, most recently from 0403018 to 7e60040 Compare May 22, 2025 08:43
@pablothedude pablothedude changed the title Fix and also run functional tests Add GSSP fallback implementation May 22, 2025
@pablothedude pablothedude marked this pull request as ready for review May 22, 2025 08:58
@pablothedude pablothedude requested a review from parijke May 22, 2025 09:56
Copy link
Contributor

@parijke parijke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We (minvws) normally disapprove PR's this big. Maximum is around 400 changes. I also see some style improvements, but we agreed that a linter should handle that.

Important: if you use mockery shouldReceive without once(), you may have passing tests with false positives.

@pablothedude
Copy link
Contributor Author

We (minvws) normally disapprove PR's this big. Maximum is around 400 changes. I also see some style improvements, but we agreed that a linter should handle that.

Important: if you use mockery shouldReceive without once(), you may have passing tests with false positives.

I agree to keep PR's as small as possible but as long as they are atomic and it adds a single functionality that would be perfectly fine.

This is done for the functional testing setup
@pablothedude pablothedude force-pushed the feature/add-azure-mfa-registration-fallback branch from 7e60040 to fd77127 Compare May 26, 2025 15:08
@pablothedude pablothedude merged commit 38ec3aa into main May 27, 2025
3 checks passed
@pablothedude pablothedude deleted the feature/add-azure-mfa-registration-fallback branch May 27, 2025 07:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants